… (re-release 0.2.2) (#18)

Re-release of 0.2.2 (originally released 2026-04-27) fixing `pg_upgrade`
compatibility with PostgreSQL 12 and 17+.

`pg_upgrade` physically copies data files and re-applies schema
definitions on
the new cluster. Any view referencing a catalog column removed in the
new
PostgreSQL version will cause the upgrade to fail. The initial 0.2.2
release
missed several such columns:

- `relhasoids` — removed from `pg_catalog.pg_class` in PG12
- `relhaspkey` — removed from `pg_catalog.pg_class` in PG17
- `attcacheoff` — removed from `pg_catalog.pg_attribute` in PG17

Those columns are removed in this release.

Also, the existing `pg-upgrade-test` CI job used `pg_upgradecluster`
(dump/restore),
which reinstalls extensions at the current version and masks exactly
this class
of problem. Replaced with binary `pg_upgrade`, which physically copies
data
files and correctly catches view/column incompatibilities across major
versions.

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

eb84bc6 Stamp 2.1.0
9fbe6f4 Fix results ordering, control file whitespace, ENABLE_* override, debug levels (Postgres-Extensions#31)
88bb4f2 Add Claude Code GitHub Actions workflows (Postgres-Extensions#41)
af5bbbb ci: pass repo owners to run-tests.yml for fork-account matching (Postgres-Extensions#40)
c7928af Fix repo-root guard to work inside a git worktree (Postgres-Extensions#39)
b062fca ci: point reusable test workflow at @master
b6cdbfd Add CI workflows and multi-session PR guard (Postgres-Extensions#33)
1ba0987 Stamp 2.0.3
1931cbe Fix pgxntool-sync remote and make it runnable without make (Postgres-Extensions#37)
8176304 Stamp 2.0.2
3e142ab Fix parse_control_file: remove comments before stripping quotes (Postgres-Extensions#27)
cacc301 Stamp 2.0.1
bf1db6b Fix bash 3.2 / Linux compatibility issues (Postgres-Extensions#26)
62d0fcb Fix broken ifeq for --load-language=plpgsql on PG < 13 (Postgres-Extensions#24)
121f0b3 Stamp 2.0.0
ad3ca7e Remove .source support; add test/install, test/build, and verify-results (Postgres-Extensions#18)
c010cf8 Fix bash 3.2 compatibility (Postgres-Extensions#23)
abeb9d3 Remove .source file support from pg_regress integration (Postgres-Extensions#22)
08c1879 Stamp 1.1.2
6e0dad2 Fix double --dbname bug that defeated unique test database names
639756c Stamp 1.1.1
6ba3176 Fix pg_tle exception handler and empty upgrade files (Postgres-Extensions#15)
3b8cb2a Stamp 1.1.0
550a901 Remove commit.md (maintained in pgxntool-test)
d73ca93 Add unique test database names to prevent conflicts (Postgres-Extensions#13)
9b344be Add update-setup-files.sh for 3-way merging after pgxntool-sync (#12)
ab7f6e2 Stamp 1.0.0
3a571ba Add pg_tle support and modernize test infrastructure (#11)
b96ea6d Add support for Claude code; build and doc improvements (#9)
e9c24de Fix pg_regress on versions > 12 (#5)

git-subtree-dir: pgxntool
git-subtree-split: eb84bc6e87e21f2ced11ff1b8ddb4028b7c67c8f

…de scripts (fixes Postgres-Extensions#28)

The machinery that generates our versioned SQL (the cat_tools--X.Y.Z.sql
install scripts and cat_tools--A.B.C--X.Y.Z.sql update scripts) from .sql.in
sources, and the DATA list that installs it, is moved out of the Makefile into
a new, documented sql.mk (included after pgxntool/base.mk so it can use
EXTENSION_VERSION_FILES, PG_CONFIG, MAJORVER, datadir, ...).

sql.mk documents the GNU Make two-phase (parse vs. recipe) hazard at the root
of Postgres-Extensions#28: we GENERATE the .sql we install, the generated files are gitignored and
absent on a clean tree at parse time, and any parse-time $(wildcard) over them
(including base.mk's DATA seed $(wildcard sql/*--*--*.sql)) silently comes up
short -- the cached directory listing means it never notices them later either.
The fix is to name-derive the install/update lists from the .sql.in SOURCES
(which DO exist at parse time), feed the generated names into DATA explicitly,
and $(sort) to dedup against base.mk's own wildcard. This makes the generated
upgrade scripts land in DATA reliably on a clean build, so `make install`
copies them and a later `ALTER EXTENSION cat_tools UPDATE` finds its path (Postgres-Extensions#28).

The historical cat_tools--0.1.* install list is no longer hardcoded: it is
derived by globbing the committed install-shaped .sql and subtracting the
update scripts and everything we generate from .sql.in. Globbing COMMITTED
files at parse time is safe; the rule of thumb is glob what git tracks,
name-derive what we generate.

Carry the Postgres-Extensions#18 pg_upgrade fix into the SOURCE. Postgres-Extensions#18 (re-release of 0.2.2) omitted
catalog columns that later PostgreSQL versions removed -- relhasoids (PG12),
relhaspkey (PG17), attcacheoff (PG17) -- so the stored view definitions do not
reference since-removed columns and binary pg_upgrade succeeds. That fix was
applied only to the GENERATED versioned files (sql/cat_tools--0.2.2.sql.in and
the *--0.2.2 update scripts), never to the SOURCE sql/cat_tools.sql.in. That was
harmless while the old Makefile deleted-and-did-not-reliably-regenerate the
current-version file, but this refactor regenerates it in place from the source,
which would REVERT the Postgres-Extensions#18 fix. Applying the same omit_column additions to
sql/cat_tools.sql.in makes regeneration reproduce sql/cat_tools--0.2.2.sql.in
byte-for-byte, preserving the released 0.2.2 SQL.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

…#38)

PR #18 (commit 31204e1, re-release 0.2.2) fixed binary `pg_upgrade`
compatibility by omitting catalog columns that newer PostgreSQL removed
from the `pg_class_v` / `pg_attribute_v` views:

- `pg_class`: omit `oid`, `relhasoids` (removed PG12), `relhaspkey`
(removed PG17)
- `pg_attribute`: add `attcacheoff` (removed PG17) to the existing
`oid`, `attmissingval`

But #18 applied that fix **only to the generated versioned files**
(`sql/cat_tools--0.2.2.sql.in` and the `*--0.2.2` update scripts),
**never to the source** `sql/cat_tools.sql.in`. So running `make`
regenerates the current-version file from source and **silently
reverts** the #18 fix.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>